Client logs collections in Configuration Manager (SCCM) – 4sysops | 您所在的位置:网站首页 › configuration manager client › Client logs collections in Configuration Manager (SCCM) – 4sysops |
Configuration Manager (previously named SCCM) supports the collection of device client logs that can be accessed through the SCCM console. These logs are very useful for troubleshooting. The console notifies the clients to collect the logs.
ContentsPrerequisitesClient log collectionOpen diagnostics logs from the SCCM consoleClean up aged diagnostic log files
Author Recent Posts Karthick JokirathinamKarthick Jokirathinam has more than 12 years of experience in enterprise client management and works as a consultant. He creates content and contributes to the community through various blogs. You can follow him on Twitter. Latest posts by Karthick Jokirathinam (see all) Client logs collections in Configuration Manager (SCCM) - Fri, Apr 7 2023 Configuration Manager upgrade: New features and installation - Thu, Jan 12 2023 Install Microsoft apps with Intune - Fri, Dec 23 2022 The following prerequisites must be met: Prerequisites The device needs to run the latest version of the Configuration Manager client. The device must be online. The admins need to have Notify resource permission. The built-in roles Full Administrators and Operation Administrator have this permission by default. Client log collectionThe site sends a client notification message to the client to upload logs. The client then sends the logs to the management point, which sends them to the site server as software inventory data. The client log size limit is 100 MB of compressed data. Once the logs are sent to the site server, you can view the logs in the resource explorer by right-clicking the client in the console. Launch the Configuration Manager console, navigate to Assets and Compliance, and select the device or device collections for which you want to view the logs. Right-click the device and then click Client Diagnostics > Collect Client Logs. The device will be notified to collect logs if it is online. Click OK to proceed with the log collection. On the client, check Diagnostics.log to verify whether the logs have been sent to the management point. The screenshot below shows that the log report was sent successfully. The MP_SinvCollFile.log contains the report forwarded from the management point to the inbox folder on the site server. The log will be copied to C:\Program Files\Microsoft Configuration Manager\inboxes\auth\sinv.box. Log collection uses the software inventory process to copy the logs from the client to the site server database. Make a note of the file name, as it will be helpful for tracking the collection process flow and for troubleshooting. Navigate to the Configuration Manager installation directory and then to inboxes > sinv.box > FileCol. You'll find the folder contains the log report. The folder name is the resource ID of the client and is unique for each client in the SCCM. You can find the resource ID for the client in the SCCM console. Right-click the client and navigate to Properties. On the General tab, search the resource ID. Another way to find the resource ID is to add a column to the collection that lists the IDs for all clients in the collection. Sinvproc.logshows the inventory file processed from the inbox folder to the database. Once the report is updated in the database, you can use the SCCM console to view/export the logs under the resource explorer on the device. Open diagnostics logs from the SCCM consoleLaunch the SCCM console, go to Assets and Compliance > Devices, select the device, right-click, and open the Resource Explorer. You can see the collected log details under Diagnostics files. The collection date, file name, and file path details are listed. You can view the logs either via the support center or by saving and extracting them. Open the logs via the Support Center. They contain details regarding Full file path, File name, and Size. Select the specific log and click Open. Right-click the collected files and save them to the folder. Extract the zip folder, and find the log file you want to investigate. The logs below are collected from the client machine under the C:\Windows\CCM\Logs folder. Clean up aged diagnostic log filesThere are two maintenance tasks available in SCCM to delete aged diagnostic logs from the site server. Subscribe to 4sysops newsletter! If you have Configuration Manager version 2006 or earlier, use the Delete Aged Collected Files site maintenance task to delete logs. If you have Configuration Manager version 2006 or later, use the Delete Aged Collected Diagnostic Files site maintenance task to delete logs.By default, the above maintenance tasks are enabled. The default value is 14 days to perform cleanup and does not delete other files. It will delete files stored under Inboxes\sinv.box\FileCol on the site server. You need to configure maintenance tasks on the primary site; they cannot be configured from the central administration site or secondary sites. Want to write for 4sysops? We are looking for new authors. 4sysops members can earn and read without ads! |
CopyRight 2018-2019 实验室设备网 版权所有 |